Fix the usage of CFG_xxxABLE_OPTIMIZE variables in Makefiles
authorAkos Kiss <akiss@inf.u-szeged.hu>
Fri, 9 Oct 2015 16:01:13 +0000 (16:01 +0000)
committerAkos Kiss <akiss@inf.u-szeged.hu>
Fri, 9 Oct 2015 16:01:13 +0000 (16:01 +0000)
commit040942265ef4b82827547ac26e5fc04895ce0b87
treed48605a2d836b0a6ea7c265e9db1269c2b451031
parent94a5b9bf30b1b6f8e7af1aee7043d7e2148a82c5
Fix the usage of CFG_xxxABLE_OPTIMIZE variables in Makefiles

Until now, there was a CFG_DISABLE_OPTIMIZE that controlled whether
`--release` is passed to cargo during the build, and a
CFG_ENABLE_OPTIMIZE that controlled where `make install` (among
others) looked for the already built cargo executable.
Unfortunately, if none of these were specified, `make all` built a
release cargo but `make install` looked for it under
`$(CFG_TARGET)/debug` (and aborted with "Please run `make` first").
This patch keeps CFG_DISABLE_OPTIMIZE only and uses it
consistently.
Makefile.in